Repository navigation
chore: lint job (ruff, hadolint, actionlint), one gate job ci, release notes with what changed - #3
Merged
Merged
Conversation
… release notes with the commits and the tool versions that changed - image/Dockerfile: bash with pipefail and arrays, as hadolint asks (DL3008 ignored: apt versions follow the dated snapshot, not pins) - README: the consumers of a pin, which tests need what, the source packages lists start with the release after 2026.11.12, ci-* tags are CI's cache, no channels
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
lintjob runs ruff (format and check, overpressure's settings in a newpyproject.toml), hadolint onimage/Dockerfileand actionlint, all pinned. hadolint's findings are fixed in the Dockerfile: bash withpipefail, and arrays instead of word splitting. DL3008 is ignored, with the reason in a comment: apt versions are not pinned one by one. The image changes, so this PR's run builds a new one.ci, needslintand both image variants and fails unless each succeeded. It becomes the only required check once this is onmain.publishneedslinttoo.image/since the release before, and per architecture the packages added, removed or at another version against itspackages-ARCH.txt.IMAGEin overpressure'soverpressure/linux.py,BUILDERin packages' workflow.ci-*tags in ghcr are CI's cache and never pinned.A new release (and the pins in overpressure and packages) will make the source-package lists true for the pinned image; that is a release step, not this PR.
Checks
check-private.py --repo . --history)Hardware
Not needed. The arm64 variant was not built locally; this PR's run builds both.